Versions:
ingress2gateway is a command-line utility released by Kubernetes SIGs that migrates existing Kubernetes Ingress configurations—including vendor-specific extensions—to the newer Gateway API format. Designed for cluster operators who need to modernize traffic-routing layers without manual rewriting, the tool parses standard Ingress objects and any accompanying provider CRDs, then emits equivalent HTTPRoute, Gateway, and ReferenceGrant resources that comply with the Gateway API specification. Typical use cases include phased upgrades from ingress controllers such as NGINX, Istio, or GKE Ingress to Gateway API implementations like Istio, Envoy Gateway, or Cilium; creating portable GitOps pipelines by standardizing on Gateway API manifests; and generating baseline YAML that can be diffed, reviewed, and gradually rolled out across staging and production clusters. The converter preserves hostname rules, path matches, TLS secrets, and annotations wherever Gateway API semantics allow, while flagging constructs that require manual intervention. Version 1.0.0, the fifth stable iteration since the project’s inception, introduces full support for v1beta1 Gateway API resources, improves handling of wildcard certificates, and adds an optional validation stage that checks output against the target implementation’s capability profile. Because it ships as a single self-contained binary for Linux, macOS, and Windows, ingress2gateway can be dropped into CI runners, local development environments, or run interactively by platform engineers preparing migration playbooks. The utility is available for free on get.nero.com, with downloads delivered through trusted Windows package sources such as winget, always providing the latest release and enabling batch installation alongside other Kubernetes tools.
Tags: